SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 62744: PROC PSMATCH stops processing or issues WARNING: The maximum likelihood estimates for the logistic regression model might not exist

DetailsAboutRate It

For some data sets, PROC PSMATCH fails to generate propensity scores and PROC LOGISTIC is able to generate them using the same model. The PSMATCH procedure issues the following warning, or stops processing and issues these errors in addition to the warning:

WARNING: The maximum likelihood estimates for the logistic regression model might not exist. The
maximum likelihood estimates are based on the last maximum likelihood iteration.
ERROR: Floating Point Overflow.
ERROR: Termination due to Floating Point Exception

To work around the problem, you can use propensity scores computed by PROC LOGISTIC in the PSDATA statement in PROC PSMATCH. For example, suppose this is your PROC PSMATCH code:

proc psmatch data=dset;
  class y A B;
  psmodel y(treated='1')=A B C;
run;

Run the same model in PROC LOGISTIC, and save the propensity scores to a data set using an OUTPUT statement:

proc logistic data=dset;
  class A B;
  model y(event='1')=A B C;
  output out=LogisticOutput p=ps;
run;

Then read the propensity score data set and specify a PSDATA statement as follows:

proc psmatch data=LogisticOutput;
  class y A B;
  psdata ps=ps treatvar=y(treated='1');
run;


Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS/STATWindows 7 Ultimate 32 bit14.215.19.4 TS1M49.4 TS1M6
Windows 7 Professional x6414.215.19.4 TS1M49.4 TS1M6
Windows 7 Professional 32 bit14.215.19.4 TS1M49.4 TS1M6
Windows 7 Home Premium x6414.215.19.4 TS1M49.4 TS1M6
Windows 7 Home Premium 32 bit14.215.19.4 TS1M49.4 TS1M6
Windows 7 Enterprise x6414.215.19.4 TS1M49.4 TS1M6
Windows 7 Enterprise 32 bit14.215.19.4 TS1M49.4 TS1M6
Microsoft Windows Server 2012 Std14.215.19.4 TS1M49.4 TS1M6
Microsoft Windows Server 2012 R2 Std14.215.19.4 TS1M49.4 TS1M6
Microsoft Windows Server 2012 R2 Datacenter14.215.19.4 TS1M49.4 TS1M6
Microsoft Windows Server 2012 Datacenter14.215.19.4 TS1M49.4 TS1M6
Microsoft Windows Server 2008 for x6414.29.4 TS1M4
Microsoft Windows Server 2008 R214.29.4 TS1M4
Microsoft Windows Server 200814.29.4 TS1M4
Microsoft Windows 1014.215.19.4 TS1M49.4 TS1M6
Microsoft Windows 8.1 Pro x6414.215.19.4 TS1M49.4 TS1M6
Microsoft Windows 8.1 Pro 32-bit14.215.19.4 TS1M49.4 TS1M6
Microsoft Windows 8.1 Enterprise x6414.215.19.4 TS1M49.4 TS1M6
Microsoft Windows 8.1 Enterprise 32-bit14.215.19.4 TS1M49.4 TS1M6
Microsoft Windows 8 Pro x6414.215.19.4 TS1M49.4 TS1M6
Microsoft Windows 8 Pro 32-bit14.215.19.4 TS1M49.4 TS1M6
Microsoft Windows 8 Enterprise x6414.215.19.4 TS1M49.4 TS1M6
Microsoft Windows 8 Enterprise 32-bit14.215.19.4 TS1M49.4 TS1M6
Microsoft® Windows® for x6414.215.19.4 TS1M49.4 TS1M6
z/OS 64-bit14.215.19.4 TS1M49.4 TS1M6
z/OS14.215.19.4 TS1M49.4 TS1M6
Windows 7 Ultimate x6414.215.19.4 TS1M49.4 TS1M6
64-bit Enabled AIX14.215.19.4 TS1M49.4 TS1M6
64-bit Enabled Solaris14.215.19.4 TS1M49.4 TS1M6
HP-UX IPF14.215.19.4 TS1M49.4 TS1M6
Linux for x6414.215.19.4 TS1M49.4 TS1M6
Solaris for x6414.215.19.4 TS1M49.4 TS1M6
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.